Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebd01fe29fa9c1706da1b16479a9b7e340e85a5eeaebcf7ae341addbf81e2ae

Tx prefix hash: cdfb2ed692d04a0271deb93751c073719459e1e90ee6d291b2c774a2c61695bc
Tx public key: a4312a3a02352141641c4c97fd37cae7aac24eabe6418d655b575f777f9cf4a2
Timestamp: 1737375784 Timestamp [UCT]: 2025-01-20 12:23:04 Age [y:d:h:m:s]: 00:335:06:45:21
Block: 1201415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237213 RingCT/type: yes/0
Extra: 01a4312a3a02352141641c4c97fd37cae7aac24eabe6418d655b575f777f9cf4a20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a15ee09c49bcf1a7611478ffe436860ae094c671050c1f62b810d5ebb2ac3f4 0.600000000000 1688066 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": 1201425, "vin": [ { "gen": { "height": 1201415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a15ee09c49bcf1a7611478ffe436860ae094c671050c1f62b810d5ebb2ac3f4" } } ], "extra": [ 1, 164, 49, 42, 58, 2, 53, 33, 65, 100, 28, 76, 151, 253, 55, 202, 231, 170, 194, 78, 171, 230, 65, 141, 101, 91, 87, 95, 119, 127, 156, 244, 162, 2, 17, 0, 0, 0, 5, 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