Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69509fff19daaa5bc4d4354d4891fbcea0631c2b1b1f4115982af4562982bb2d

Tx prefix hash: 082afe64b1bb959866f49076719bbd165dc698088d39553356c6f3b8057b7943
Tx public key: 18ae9e15d8f1ecfbaa0ecfbab51cadc9405a80e19b7fa008ea10ac0342d7eeee
Timestamp: 1703024158 Timestamp [UCT]: 2023-12-19 22:15:58 Age [y:d:h:m:s]: 01:329:15:27:19
Block: 916821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494442 RingCT/type: yes/0
Extra: 0118ae9e15d8f1ecfbaa0ecfbab51cadc9405a80e19b7fa008ea10ac0342d7eeee021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41412c3b2b9c1b783b800dc8b5936b94e8fb7f8a3973def0f928f9b28424892e 0.600000000000 1374381 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": 916831, "vin": [ { "gen": { "height": 916821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41412c3b2b9c1b783b800dc8b5936b94e8fb7f8a3973def0f928f9b28424892e" } } ], "extra": [ 1, 24, 174, 158, 21, 216, 241, 236, 251, 170, 14, 207, 186, 181, 28, 173, 201, 64, 90, 128, 225, 155, 127, 160, 8, 234, 16, 172, 3, 66, 215, 238, 238, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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