Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904b7316333be068abf2242c6f7e47a932e3536515a5b4292392dd8f4fd9fb00

Tx prefix hash: d7611f10bfeb7ddbb6192eda83fd71f995214b20e608c418d954d28120ab09f6
Tx public key: 3a70008fff254b14e85d0adde36c3bae37d380a0765c528c12fb19cc12c4f2fb
Timestamp: 1733793648 Timestamp [UCT]: 2024-12-10 01:20:48 Age [y:d:h:m:s]: 00:108:22:54:12
Block: 1171814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77659 RingCT/type: yes/0
Extra: 013a70008fff254b14e85d0adde36c3bae37d380a0765c528c12fb19cc12c4f2fb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d7a40265e66926c7b84385d90442303ba524cd86f25f0d4ca3f90282cf77665 0.600000000000 1657621 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": 1171824, "vin": [ { "gen": { "height": 1171814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d7a40265e66926c7b84385d90442303ba524cd86f25f0d4ca3f90282cf77665" } } ], "extra": [ 1, 58, 112, 0, 143, 255, 37, 75, 20, 232, 93, 10, 221, 227, 108, 59, 174, 55, 211, 128, 160, 118, 92, 82, 140, 18, 251, 25, 204, 18, 196, 242, 251, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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