Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e53522edc0c8eaf5f977a8b31e81ab01e710b0c3c5ad5e7732727aafd249a1

Tx prefix hash: 8c024e129e499bfa3074a05df867e160e2315c185dfeee54b65973dd96fa2b23
Tx public key: 4753e8cac1f793be74ab4bcd2656e7ff1e77bc5e5ba0e2c5eca5a57279f75136
Timestamp: 1739573570 Timestamp [UCT]: 2025-02-14 22:52:50 Age [y:d:h:m:s]: 00:027:02:04:29
Block: 1219399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19379 RingCT/type: yes/0
Extra: 014753e8cac1f793be74ab4bcd2656e7ff1e77bc5e5ba0e2c5eca5a57279f751360211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de129c17b36d127973a0c2c7b0691284ad7acc8ffa80870d6216e35c8bc0fdc4 0.600000000000 1706224 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": 1219409, "vin": [ { "gen": { "height": 1219399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de129c17b36d127973a0c2c7b0691284ad7acc8ffa80870d6216e35c8bc0fdc4" } } ], "extra": [ 1, 71, 83, 232, 202, 193, 247, 147, 190, 116, 171, 75, 205, 38, 86, 231, 255, 30, 119, 188, 94, 91, 160, 226, 197, 236, 165, 165, 114, 121, 247, 81, 54, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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