Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c25b667539cfa59d4dc86ffaab587f83d78b4f243ac9b50e23b0017a5790ff

Tx prefix hash: 0d64ffaa8e9886418cb126e03c732c9f37f970197b71afb96a9341e6ab65bcc4
Tx public key: 9909228088f987db280b102dfd6ac7011ec1569e263c1c4b136f9b3562f17fb4
Timestamp: 1718885698 Timestamp [UCT]: 2024-06-20 12:14:58 Age [y:d:h:m:s]: 01:139:11:58:37
Block: 1048325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358231 RingCT/type: yes/0
Extra: 019909228088f987db280b102dfd6ac7011ec1569e263c1c4b136f9b3562f17fb402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c64b7b08dbefc6edc84dd8431309f9b7396e31148cb0dc182e0df668117bcd5 0.600000000000 1518382 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": 1048335, "vin": [ { "gen": { "height": 1048325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c64b7b08dbefc6edc84dd8431309f9b7396e31148cb0dc182e0df668117bcd5" } } ], "extra": [ 1, 153, 9, 34, 128, 136, 249, 135, 219, 40, 11, 16, 45, 253, 106, 199, 1, 30, 193, 86, 158, 38, 60, 28, 75, 19, 111, 155, 53, 98, 241, 127, 180, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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