Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7faa62d8f269bd89499aa53526b80523fb2087596b33b957c4f25a427ae14be0

Tx prefix hash: c00e235dfb190e0f8bf2e2f1f8236868999b194493274c9c80d9527013d11cc8
Tx public key: d1d27f4f69a7cd896b9171b623f86889f0ca18e9d9ed0438427fbdef5a2bc798
Timestamp: 1720299721 Timestamp [UCT]: 2024-07-06 21:02:01 Age [y:d:h:m:s]: 00:199:22:51:09
Block: 1060034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143032 RingCT/type: yes/0
Extra: 01d1d27f4f69a7cd896b9171b623f86889f0ca18e9d9ed0438427fbdef5a2bc79802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 530d58d19adeac06b358c5dc4cccfb8bacba994e1cd5f48f464e861188ee3eb1 0.600000000000 1530505 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": 1060044, "vin": [ { "gen": { "height": 1060034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "530d58d19adeac06b358c5dc4cccfb8bacba994e1cd5f48f464e861188ee3eb1" } } ], "extra": [ 1, 209, 210, 127, 79, 105, 167, 205, 137, 107, 145, 113, 182, 35, 248, 104, 137, 240, 202, 24, 233, 217, 237, 4, 56, 66, 127, 189, 239, 90, 43, 199, 152, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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