Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6350a9c5626c9ea157ae2dbb3dccd27a46805b7fa1eb3ca4d596883dc1975e2

Tx prefix hash: 6383504fb51c479d27dc6be7f576f14e8a65fce72e8d4b12c009e070d2aee39c
Tx public key: 871290f7cce4ff3c77cc0477c7cee97ffa8d8948298f0213800fa4d3266f522b
Timestamp: 1702379345 Timestamp [UCT]: 2023-12-12 11:09:05 Age [y:d:h:m:s]: 01:337:09:51:14
Block: 911488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499993 RingCT/type: yes/0
Extra: 01871290f7cce4ff3c77cc0477c7cee97ffa8d8948298f0213800fa4d3266f522b02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b1b2a4bb6864c47d634a15718f36bf271ff91b7b265279282e22c05a06c234 0.600000000000 1368692 of 15

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": 911498, "vin": [ { "gen": { "height": 911488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b1b2a4bb6864c47d634a15718f36bf271ff91b7b265279282e22c05a06c234" } } ], "extra": [ 1, 135, 18, 144, 247, 204, 228, 255, 60, 119, 204, 4, 119, 199, 206, 233, 127, 250, 141, 137, 72, 41, 143, 2, 19, 128, 15, 164, 211, 38, 111, 82, 43, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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