Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c21365925fe75a9fa1d99763832a1bb5c3e926dc0952e14b4be4c05d5ab80e38

Tx prefix hash: 3d31ce8eabf7fa8f916d35481c2c6bc2b5892285c23725893bd76a698d8aed79
Tx public key: f091151c9a88206c19f27fc0022a4c8e62131560dab8553daf1d2f4eaacf38ae
Timestamp: 1728026694 Timestamp [UCT]: 2024-10-04 07:24:54 Age [y:d:h:m:s]: 00:171:22:16:10
Block: 1124109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122653 RingCT/type: yes/0
Extra: 01f091151c9a88206c19f27fc0022a4c8e62131560dab8553daf1d2f4eaacf38ae021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d3b4eb1755fc0061e04d119e74eaedef7ebf9267c91bb74b17dec29fc09b07d 0.600000000000 1606678 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": 1124119, "vin": [ { "gen": { "height": 1124109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d3b4eb1755fc0061e04d119e74eaedef7ebf9267c91bb74b17dec29fc09b07d" } } ], "extra": [ 1, 240, 145, 21, 28, 154, 136, 32, 108, 25, 242, 127, 192, 2, 42, 76, 142, 98, 19, 21, 96, 218, 184, 85, 61, 175, 29, 47, 78, 170, 207, 56, 174, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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