Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58c7a6dfee5767317c3852502625ee313ead359fa17d86dfb7e214c76bd95bd4

Tx prefix hash: f6999d7ba5e594fba1c0db9b30378c037c418e9834ba5e4d255f0e2c0221a3fb
Tx public key: 848a1f42949b99404be60f3f9d7415fea191be2faa51af542913903829de6336
Timestamp: 1718866756 Timestamp [UCT]: 2024-06-20 06:59:16 Age [y:d:h:m:s]: 00:272:04:43:01
Block: 1048160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194516 RingCT/type: yes/0
Extra: 01848a1f42949b99404be60f3f9d7415fea191be2faa51af542913903829de63360211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca68c7ff9a92f3a07c3aa318ac506dbf73106ea64a873a62b6c213d41d5bca92 0.600000000000 1518171 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": 1048170, "vin": [ { "gen": { "height": 1048160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca68c7ff9a92f3a07c3aa318ac506dbf73106ea64a873a62b6c213d41d5bca92" } } ], "extra": [ 1, 132, 138, 31, 66, 148, 155, 153, 64, 75, 230, 15, 63, 157, 116, 21, 254, 161, 145, 190, 47, 170, 81, 175, 84, 41, 19, 144, 56, 41, 222, 99, 54, 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