Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c667597c06d1c113243e243ba248519212d798f235ef82b2cddd5d9e087fd7c

Tx prefix hash: 738b014964386c144c4f8cdab59aa0f07f4796457b6cb3d29a679a0912828931
Tx public key: 62ffebd3983d9a66423cf55b2e29b2343f8e3c54cf6217e5f7d61e60c4cbf6e5
Timestamp: 1719097475 Timestamp [UCT]: 2024-06-22 23:04:35 Age [y:d:h:m:s]: 00:358:10:55:07
Block: 1050054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256108 RingCT/type: yes/0
Extra: 0162ffebd3983d9a66423cf55b2e29b2343f8e3c54cf6217e5f7d61e60c4cbf6e502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bd1499bafc65e4f4b18fafa4e2d166115519092a9767c34fd1d4ee1d799bb04 0.600000000000 1520205 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": 1050064, "vin": [ { "gen": { "height": 1050054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bd1499bafc65e4f4b18fafa4e2d166115519092a9767c34fd1d4ee1d799bb04" } } ], "extra": [ 1, 98, 255, 235, 211, 152, 61, 154, 102, 66, 60, 245, 91, 46, 41, 178, 52, 63, 142, 60, 84, 207, 98, 23, 229, 247, 214, 30, 96, 196, 203, 246, 229, 2, 17, 0, 0, 0, 4, 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