Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225f5622f97e1913ac8bb9e814db1aaa7d67970fc9f28afdc9e44cbefdd42f55

Tx prefix hash: 7f5666bb85d54e12a9ae68a06266c9a55ed82de13d02ec826472f8f2ad56e0a3
Tx public key: cf436227ba5108d73f0c8a348ea09feef21317d58222c15837390af0498b075a
Timestamp: 1722360240 Timestamp [UCT]: 2024-07-30 17:24:00 Age [y:d:h:m:s]: 01:099:07:11:06
Block: 1077121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329444 RingCT/type: yes/0
Extra: 01cf436227ba5108d73f0c8a348ea09feef21317d58222c15837390af0498b075a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c5e85db972bed3bfc4a9c1fc6857180df5760ea7eaa7db735e00fc84f9e5ab4 0.600000000000 1549666 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": 1077131, "vin": [ { "gen": { "height": 1077121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c5e85db972bed3bfc4a9c1fc6857180df5760ea7eaa7db735e00fc84f9e5ab4" } } ], "extra": [ 1, 207, 67, 98, 39, 186, 81, 8, 215, 63, 12, 138, 52, 142, 160, 159, 238, 242, 19, 23, 213, 130, 34, 193, 88, 55, 57, 10, 240, 73, 139, 7, 90, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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