Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9348ab490078e2c5fdbcf828c95e0cc68cae19cb0ef30eb3404c9d1b68ba6a7

Tx prefix hash: 6eed156db72096b7a1d54276e1b138fb849c6b79dec83727c4744394278949cd
Tx public key: 12d61bfaef1cbe967103d0545b01af00a5a57197e01b08d517939d9e99e4df6e
Timestamp: 1721149311 Timestamp [UCT]: 2024-07-16 17:01:51 Age [y:d:h:m:s]: 01:113:04:33:18
Block: 1067104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339372 RingCT/type: yes/0
Extra: 0112d61bfaef1cbe967103d0545b01af00a5a57197e01b08d517939d9e99e4df6e02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d457b9cbab638415a0ae4a2e09466e9c3d83de03e7843ad0d6aba900eeb4f9c 0.600000000000 1537827 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": 1067114, "vin": [ { "gen": { "height": 1067104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d457b9cbab638415a0ae4a2e09466e9c3d83de03e7843ad0d6aba900eeb4f9c" } } ], "extra": [ 1, 18, 214, 27, 250, 239, 28, 190, 150, 113, 3, 208, 84, 91, 1, 175, 0, 165, 165, 113, 151, 224, 27, 8, 213, 23, 147, 157, 158, 153, 228, 223, 110, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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