Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b001b57f56f82814fb1bbf4bdbf3f4885a34e4d2648b84303fe94e61daeece39

Tx prefix hash: 4f6f97e37d4fdfabfc2b1df693701e9f83e3527670175c6b12d23b573f0fdafe
Tx public key: aac46dbdbc96250fc87274f0af83c8a4b27cea7a683b21fb80011e8ad38fa3af
Timestamp: 1718906105 Timestamp [UCT]: 2024-06-20 17:55:05 Age [y:d:h:m:s]: 01:140:15:46:07
Block: 1048478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359088 RingCT/type: yes/0
Extra: 01aac46dbdbc96250fc87274f0af83c8a4b27cea7a683b21fb80011e8ad38fa3af0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b6b84db58b03d17cc3b90ab91c970ee3b5d8c5742a0ecd40baf4aff413576d 0.600000000000 1518563 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": 1048488, "vin": [ { "gen": { "height": 1048478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b6b84db58b03d17cc3b90ab91c970ee3b5d8c5742a0ecd40baf4aff413576d" } } ], "extra": [ 1, 170, 196, 109, 189, 188, 150, 37, 15, 200, 114, 116, 240, 175, 131, 200, 164, 178, 124, 234, 122, 104, 59, 33, 251, 128, 1, 30, 138, 211, 143, 163, 175, 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