Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b890bf154729a0276ed3718192b8eba69b793d2a7263a0c47c74989d4ea910a1

Tx prefix hash: 60b6d32ba303f712a7df9513870197db0df407f1f46a9d9afe26e2a221383cfc
Tx public key: 85ec0f50d5d8d26d54bcc889d784ba45ea08cd02d33535fa005b767fa12cdd4d
Timestamp: 1709580402 Timestamp [UCT]: 2024-03-04 19:26:42 Age [y:d:h:m:s]: 00:313:00:39:11
Block: 971176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224066 RingCT/type: yes/0
Extra: 0185ec0f50d5d8d26d54bcc889d784ba45ea08cd02d33535fa005b767fa12cdd4d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd2b9874482d1e097c6e4cb8ac357a40967a40cce0fe9a39eca38f3df1680764 0.600000000000 1431061 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": 971186, "vin": [ { "gen": { "height": 971176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd2b9874482d1e097c6e4cb8ac357a40967a40cce0fe9a39eca38f3df1680764" } } ], "extra": [ 1, 133, 236, 15, 80, 213, 216, 210, 109, 84, 188, 200, 137, 215, 132, 186, 69, 234, 8, 205, 2, 211, 53, 53, 250, 0, 91, 118, 127, 161, 44, 221, 77, 2, 17, 0, 0, 0, 1, 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