Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e5b2f88257b8846438b80c8dfaa79ec992b09a0cf3eaf88f97b53fe74d21e4

Tx prefix hash: 1c41dd89d26eefd3c2e4541a445a9abf787fbeae351d0441287cd7692113ee20
Tx public key: e5ab771a0c040ffe7243274e8721d41204a60e6ea2063e0db7e7b3e1dd02f727
Timestamp: 1750834976 Timestamp [UCT]: 2025-06-25 07:02:56 Age [y:d:h:m:s]: 00:148:14:46:21
Block: 1312361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104151 RingCT/type: yes/0
Extra: 01e5ab771a0c040ffe7243274e8721d41204a60e6ea2063e0db7e7b3e1dd02f72702110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 638b47fd8eb80e4e4807ab899db68bd08a774b479f8c74e3c2bd8b79f03ad241 0.600000000000 1799994 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": 1312371, "vin": [ { "gen": { "height": 1312361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "638b47fd8eb80e4e4807ab899db68bd08a774b479f8c74e3c2bd8b79f03ad241" } } ], "extra": [ 1, 229, 171, 119, 26, 12, 4, 15, 254, 114, 67, 39, 78, 135, 33, 212, 18, 4, 166, 14, 110, 162, 6, 62, 13, 183, 231, 179, 225, 221, 2, 247, 39, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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