Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bbf32ee819167e29253adc40c146b0ac0cb3e5a5748f5c38a6d2475668f7346

Tx prefix hash: 19dc595ca07d93875a603fdcd308c9049113c1e460b1c3e5ed51b2a494c2705f
Tx public key: 42214d7d697b3beba5541707ceffe165d5cd8a1573a1f6208c5c89572af29e2a
Timestamp: 1709060924 Timestamp [UCT]: 2024-02-27 19:08:44 Age [y:d:h:m:s]: 01:074:16:50:56
Block: 966875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314417 RingCT/type: yes/0
Extra: 0142214d7d697b3beba5541707ceffe165d5cd8a1573a1f6208c5c89572af29e2a0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f8a1226e298f0d9f9ae4d8e5dc1f32186aeebcd1a23e160bf694864a8ed4cf0 0.600000000000 1426646 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": 966885, "vin": [ { "gen": { "height": 966875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f8a1226e298f0d9f9ae4d8e5dc1f32186aeebcd1a23e160bf694864a8ed4cf0" } } ], "extra": [ 1, 66, 33, 77, 125, 105, 123, 59, 235, 165, 84, 23, 7, 206, 255, 225, 101, 213, 205, 138, 21, 115, 161, 246, 32, 140, 92, 137, 87, 42, 242, 158, 42, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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