Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4dc2150d452c613bee1362e80827af394f1646fdefc3554b1faecb9af0d36f5

Tx prefix hash: 16a88553b8482a0da6a40b7cf0116607f68ed1fa0a3d092322ad08b701ace1d0
Tx public key: f5738f1a3a6c8114f7d157320b3cfcb0668e3e861fb94ee830d66a5321e37324
Timestamp: 1706224995 Timestamp [UCT]: 2024-01-25 23:23:15 Age [y:d:h:m:s]: 01:030:22:03:16
Block: 943326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283158 RingCT/type: yes/0
Extra: 01f5738f1a3a6c8114f7d157320b3cfcb0668e3e861fb94ee830d66a5321e3732402110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbd111852ae0f9efeb11af6edb4effd3ed582b7716640236926843984dac25dd 0.600000000000 1401532 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": 943336, "vin": [ { "gen": { "height": 943326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbd111852ae0f9efeb11af6edb4effd3ed582b7716640236926843984dac25dd" } } ], "extra": [ 1, 245, 115, 143, 26, 58, 108, 129, 20, 247, 209, 87, 50, 11, 60, 252, 176, 102, 142, 62, 134, 31, 185, 78, 232, 48, 214, 106, 83, 33, 227, 115, 36, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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