Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e3f17fba6d19c360b201bab16c010b56b43ae91c3e08612bb1e1295d8ed914a

Tx prefix hash: 395370420bb39e1c1302abf141e0a6d678437514ab265a91f97c8c49627f8d79
Tx public key: d59c832f367589cb38351be7b245e2385643ff10c4327bd37ff852f51f067fc4
Timestamp: 1738132292 Timestamp [UCT]: 2025-01-29 06:31:32 Age [y:d:h:m:s]: 00:293:03:34:31
Block: 1207460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207279 RingCT/type: yes/0
Extra: 01d59c832f367589cb38351be7b245e2385643ff10c4327bd37ff852f51f067fc40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d2eaa05a2ecfd5504c0bea75d7710e6fcfb69ef9e64765d22f420cccb60b0f9 0.600000000000 1694183 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": 1207470, "vin": [ { "gen": { "height": 1207460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d2eaa05a2ecfd5504c0bea75d7710e6fcfb69ef9e64765d22f420cccb60b0f9" } } ], "extra": [ 1, 213, 156, 131, 47, 54, 117, 137, 203, 56, 53, 27, 231, 178, 69, 226, 56, 86, 67, 255, 16, 196, 50, 123, 211, 127, 248, 82, 245, 31, 6, 127, 196, 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