Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00780f402f9a8b8a5436dc071c93b78af439694575ca918f70dc1ba0eb7851cf

Tx prefix hash: 661adc11adc1b3c98b2550c8178790908b17aed7080d7fe51e91f05a79903f62
Tx public key: ed202ff7356e7a574509fe18631d16411dfc91be955c17f76ea5b79a5298b8a4
Timestamp: 1755931421 Timestamp [UCT]: 2025-08-23 06:43:41 Age [y:d:h:m:s]: 00:090:05:36:11
Block: 1352522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64417 RingCT/type: yes/0
Extra: 01ed202ff7356e7a574509fe18631d16411dfc91be955c17f76ea5b79a5298b8a40211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e352b705f5c80776618676808d61baf2f2e352c1a4e272a1a4abc8c880aca226 0.600000000000 1840487 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": 1352532, "vin": [ { "gen": { "height": 1352522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e352b705f5c80776618676808d61baf2f2e352c1a4e272a1a4abc8c880aca226" } } ], "extra": [ 1, 237, 32, 47, 247, 53, 110, 122, 87, 69, 9, 254, 24, 99, 29, 22, 65, 29, 252, 145, 190, 149, 92, 23, 247, 110, 165, 183, 154, 82, 152, 184, 164, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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