Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b470de166acb22129eedebff5e40fcc2607601ced83c9496ad7bb7ed47ef1cbf

Tx prefix hash: 3a987b2b3aec6feef59ef479d6e44fe569f104b7aa6c73f779aed5ddcc980155
Tx public key: b79e5444aa569d28b2e7f8c79c233f224e15d45b8bd4e8027ce2c80754d76408
Timestamp: 1728261038 Timestamp [UCT]: 2024-10-07 00:30:38 Age [y:d:h:m:s]: 00:222:07:37:16
Block: 1126044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158711 RingCT/type: yes/0
Extra: 01b79e5444aa569d28b2e7f8c79c233f224e15d45b8bd4e8027ce2c80754d7640802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc259f1fc6914ddf792f2725ac95012e77ff9f8b24e21a69f872e3ae5f46aa2 0.600000000000 1608817 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": 1126054, "vin": [ { "gen": { "height": 1126044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc259f1fc6914ddf792f2725ac95012e77ff9f8b24e21a69f872e3ae5f46aa2" } } ], "extra": [ 1, 183, 158, 84, 68, 170, 86, 157, 40, 178, 231, 248, 199, 156, 35, 63, 34, 78, 21, 212, 91, 139, 212, 232, 2, 124, 226, 200, 7, 84, 215, 100, 8, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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