Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8d9abc65075436a6b236f9e358f097d61f9515c33319bd441858d58ffcb8f58

Tx prefix hash: fdcb0c47229b890c13dee5a1f6d4cffd650d592062407e13fb94e601827210e8
Tx public key: 7972ba967b9ab6e7127da31d8339a3064eacb2b238871c031d128a838fddfb8d
Timestamp: 1711588296 Timestamp [UCT]: 2024-03-28 01:11:36 Age [y:d:h:m:s]: 01:227:23:27:38
Block: 987834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421612 RingCT/type: yes/0
Extra: 017972ba967b9ab6e7127da31d8339a3064eacb2b238871c031d128a838fddfb8d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bea6aee0c2f1c671cac5b78c8bdc648006fee054f6900ab87a317919f1f0799 0.600000000000 1448093 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": 987844, "vin": [ { "gen": { "height": 987834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bea6aee0c2f1c671cac5b78c8bdc648006fee054f6900ab87a317919f1f0799" } } ], "extra": [ 1, 121, 114, 186, 150, 123, 154, 182, 231, 18, 125, 163, 29, 131, 57, 163, 6, 78, 172, 178, 178, 56, 135, 28, 3, 29, 18, 138, 131, 143, 221, 251, 141, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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