Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de77b5532c3ad2e4b3373c9a808b9bc45303f746cddc788aafab08faeb59e85

Tx prefix hash: 883cd62799eb58661ae8e2be23374ed6a051e994bbe7a9c2e231d675e91db890
Tx public key: e4ddd88ae803bf9fe924317e1a98e531a14d39231c3f77bbb07a76ecf7fb9fe1
Timestamp: 1726938092 Timestamp [UCT]: 2024-09-21 17:01:32 Age [y:d:h:m:s]: 00:192:03:09:41
Block: 1115071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137125 RingCT/type: yes/0
Extra: 01e4ddd88ae803bf9fe924317e1a98e531a14d39231c3f77bbb07a76ecf7fb9fe102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14fcec7d0f038d84c3125051369da3bf6d58c80d92e4bb106354a8153b43b837 0.600000000000 1595078 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": 1115081, "vin": [ { "gen": { "height": 1115071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14fcec7d0f038d84c3125051369da3bf6d58c80d92e4bb106354a8153b43b837" } } ], "extra": [ 1, 228, 221, 216, 138, 232, 3, 191, 159, 233, 36, 49, 126, 26, 152, 229, 49, 161, 77, 57, 35, 28, 63, 119, 187, 176, 122, 118, 236, 247, 251, 159, 225, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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