Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e423c3d86b2fa0da5773cccbaadf54c980f5aae9aa3a9e779a7c75694001193d

Tx prefix hash: 8f9daa5177ca4c04c2b1f986bafbb50daa9a69fadabbcf337976bf09d79b44b7
Tx public key: 28a53a2685715006bafce7c9ff0065176240aad872ae82e8bd74698dfb2529d8
Timestamp: 1718434011 Timestamp [UCT]: 2024-06-15 06:46:51 Age [y:d:h:m:s]: 00:209:21:56:25
Block: 1044580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150212 RingCT/type: yes/0
Extra: 0128a53a2685715006bafce7c9ff0065176240aad872ae82e8bd74698dfb2529d8021100000001cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b82755811d85972439acf4e5d45a46d9a5c80c2b08c3ffbbb74b37d2acb6898 0.600000000000 1513927 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": 1044590, "vin": [ { "gen": { "height": 1044580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b82755811d85972439acf4e5d45a46d9a5c80c2b08c3ffbbb74b37d2acb6898" } } ], "extra": [ 1, 40, 165, 58, 38, 133, 113, 80, 6, 186, 252, 231, 201, 255, 0, 101, 23, 98, 64, 170, 216, 114, 174, 130, 232, 189, 116, 105, 141, 251, 37, 41, 216, 2, 17, 0, 0, 0, 1, 205, 99, 251, 27, 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