Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bbfaf1608cc272ae3bd01bbe3cd7aabd7d3af6112123f9b8d4926cdd104877c5

Tx prefix hash: b7fbb060ed4792dbaef90c78c1d4e8ff5fe11250ded7da1930a83a5978072376
Tx public key: b0ce60f9003a49ce26944d5a6fb4c48de859e8e7877717373c90bd64cc5b2f26
Timestamp: 1634619960 Timestamp [UCT]: 2021-10-19 05:06:00 Age [y:d:h:m:s]: 03:031:12:17:01
Block: 355956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 800570 RingCT/type: yes/0
Extra: 01b0ce60f9003a49ce26944d5a6fb4c48de859e8e7877717373c90bd64cc5b2f260211000000478d0de867000000000000000000

1 output(s) for total of 40.604149909000 dcy

stealth address amount amount idx
00: e4ba4c73ea93ac56ffb8c308c8fc0d3438d4fcca1bc1d9a9ebfaf3868cc8d822 40.604149909000 726480 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 355966, "vin": [ { "gen": { "height": 355956 } } ], "vout": [ { "amount": 40604149909, "target": { "key": "e4ba4c73ea93ac56ffb8c308c8fc0d3438d4fcca1bc1d9a9ebfaf3868cc8d822" } } ], "extra": [ 1, 176, 206, 96, 249, 0, 58, 73, 206, 38, 148, 77, 90, 111, 180, 196, 141, 232, 89, 232, 231, 135, 119, 23, 55, 60, 144, 189, 100, 204, 91, 47, 38, 2, 17, 0, 0, 0, 71, 141, 13, 232, 103, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8