Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a69dd6d68207f965e84195f04d11fe6adea72624cee294d25a561ba2f4ac257a

Tx prefix hash: 953659294f99fe80c771fc4318b80b74c7ccb40847e85525961e77eab2715cfd
Tx public key: 32925aa6440907a299a1beebf8b3335ea078c83ecbe83e922c8d0bce130ae554
Timestamp: 1732784284 Timestamp [UCT]: 2024-11-28 08:58:04 Age [y:d:h:m:s]: 00:124:04:21:57
Block: 1163449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88543 RingCT/type: yes/0
Extra: 0132925aa6440907a299a1beebf8b3335ea078c83ecbe83e922c8d0bce130ae5540211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b3da5c94d62afc548e4858e8d4bfefd1c9ee0b628b4f1ab91b80aef2532dbe9 0.600000000000 1649116 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": 1163459, "vin": [ { "gen": { "height": 1163449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b3da5c94d62afc548e4858e8d4bfefd1c9ee0b628b4f1ab91b80aef2532dbe9" } } ], "extra": [ 1, 50, 146, 90, 166, 68, 9, 7, 162, 153, 161, 190, 235, 248, 179, 51, 94, 160, 120, 200, 62, 203, 232, 62, 146, 44, 141, 11, 206, 19, 10, 229, 84, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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