Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f229e7aa45d6942ab648bbcba684ae7d13c97fcdaaf7e81c8f27ca68cc1c655

Tx prefix hash: 4ce61fa8d65963de6df55981aa6ca732b79326e2b8db81d79c303091c538645e
Tx public key: 05633c0b0c9d3e3d711618f8477e7d372a227dee965bba8d3f88a57228fd196f
Timestamp: 1713469865 Timestamp [UCT]: 2024-04-18 19:51:05 Age [y:d:h:m:s]: 01:022:07:28:03
Block: 1003404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276917 RingCT/type: yes/0
Extra: 0105633c0b0c9d3e3d711618f8477e7d372a227dee965bba8d3f88a57228fd196f021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a593470b866330fc4d1c623954e4db136755a8c0b605b6a0af9d859dae905acd 0.600000000000 1463934 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": 1003414, "vin": [ { "gen": { "height": 1003404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a593470b866330fc4d1c623954e4db136755a8c0b605b6a0af9d859dae905acd" } } ], "extra": [ 1, 5, 99, 60, 11, 12, 157, 62, 61, 113, 22, 24, 248, 71, 126, 125, 55, 42, 34, 125, 238, 150, 91, 186, 141, 63, 136, 165, 114, 40, 253, 25, 111, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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