Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adadcbf7d3d1b730da63faf88b455ddc99462ce9db880bb80e085edd5c6a0126

Tx prefix hash: 989080ff59965eee69b07c48de0a0b1f61a3c5332c5194ad461d55a8ceceec9e
Tx public key: 8e149da2316f1d92c8c4d2bef1467ae130e410f4cf436395753b5fefd78df51e
Timestamp: 1706461413 Timestamp [UCT]: 2024-01-28 17:03:33 Age [y:d:h:m:s]: 01:063:07:51:08
Block: 945290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306340 RingCT/type: yes/0
Extra: 018e149da2316f1d92c8c4d2bef1467ae130e410f4cf436395753b5fefd78df51e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7cfdcdba38a4c75d94719beb3026ac486efc156420f165556d9883a05931f53 0.600000000000 1403602 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": 945300, "vin": [ { "gen": { "height": 945290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7cfdcdba38a4c75d94719beb3026ac486efc156420f165556d9883a05931f53" } } ], "extra": [ 1, 142, 20, 157, 162, 49, 111, 29, 146, 200, 196, 210, 190, 241, 70, 122, 225, 48, 228, 16, 244, 207, 67, 99, 149, 117, 59, 95, 239, 215, 141, 245, 30, 2, 17, 0, 0, 0, 5, 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