Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea214fcbae41ccfa78bde99d678b39906d5d3f3006c8fee0db403ac4123a2ae

Tx prefix hash: 291c7608c9b9790fe62cb295f46f9e2def24606744f7495e66c1cb3da06e32ef
Tx public key: 3726e8a9528f31686aab68e97f02da790d9f3b85930eb4f1c0bbd33220ffcbc8
Timestamp: 1705282876 Timestamp [UCT]: 2024-01-15 01:41:16 Age [y:d:h:m:s]: 01:155:17:07:22
Block: 935513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372314 RingCT/type: yes/0
Extra: 013726e8a9528f31686aab68e97f02da790d9f3b85930eb4f1c0bbd33220ffcbc80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d17656d4b68bd4af7497bef301ddbcd1d033c84b7dbad4b8e11817d71189fa 0.600000000000 1393529 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": 935523, "vin": [ { "gen": { "height": 935513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d17656d4b68bd4af7497bef301ddbcd1d033c84b7dbad4b8e11817d71189fa" } } ], "extra": [ 1, 55, 38, 232, 169, 82, 143, 49, 104, 106, 171, 104, 233, 127, 2, 218, 121, 13, 159, 59, 133, 147, 14, 180, 241, 192, 187, 211, 50, 32, 255, 203, 200, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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