Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f89c004a6f3bfad7c2029df4d7ea827492e2082f9a1ee5b3e242650531703e85

Tx prefix hash: fd56b5af16877d76264e78570dc8543ab47ac06391664d19f38a5fe2d3ecb88e
Tx public key: 4283a36f6bf9a6b6202d60b1e3a0e2c0d6fff1d2058d5c021b1e91b8a61e7ffb
Timestamp: 1706411623 Timestamp [UCT]: 2024-01-28 03:13:43 Age [y:d:h:m:s]: 01:343:21:07:45
Block: 944877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504672 RingCT/type: yes/0
Extra: 014283a36f6bf9a6b6202d60b1e3a0e2c0d6fff1d2058d5c021b1e91b8a61e7ffb02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0399308f18642317601efb60c86c4f80edb469c108ba841b66df11205a2531a6 0.600000000000 1403169 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": 944887, "vin": [ { "gen": { "height": 944877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0399308f18642317601efb60c86c4f80edb469c108ba841b66df11205a2531a6" } } ], "extra": [ 1, 66, 131, 163, 111, 107, 249, 166, 182, 32, 45, 96, 177, 227, 160, 226, 192, 214, 255, 241, 210, 5, 141, 92, 2, 27, 30, 145, 184, 166, 30, 127, 251, 2, 17, 0, 0, 0, 8, 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