Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec188ac267a829748a1fd5cbd51f5d1b313ed2c3d5eeb5307ab7b4838d88d838

Tx prefix hash: a302f6a61b9ea270defdf870d1f43945404db05546c47705106815b47cf661e5
Tx public key: 63d8f1890fa3490ae61c53a67884212c6e7962c465fa73e6b1e9b5f5175d31b5
Timestamp: 1750857339 Timestamp [UCT]: 2025-06-25 13:15:39 Age [y:d:h:m:s]: 00:141:19:34:51
Block: 1312539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99301 RingCT/type: yes/0
Extra: 0163d8f1890fa3490ae61c53a67884212c6e7962c465fa73e6b1e9b5f5175d31b502110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 736c509acd7a8d4663edc34ee2621584c43b29162b7915e207129e0952402035 0.600000000000 1800172 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": 1312549, "vin": [ { "gen": { "height": 1312539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "736c509acd7a8d4663edc34ee2621584c43b29162b7915e207129e0952402035" } } ], "extra": [ 1, 99, 216, 241, 137, 15, 163, 73, 10, 230, 28, 83, 166, 120, 132, 33, 44, 110, 121, 98, 196, 101, 250, 115, 230, 177, 233, 181, 245, 23, 93, 49, 181, 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