Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba6183e4c23e090b27e5a3dd8d7fa1c2e22d5441d6617b9acd2e517cd260f105

Tx prefix hash: 65cd228cd11ec7561ee6b2608eaaadc0182bbe2b0146be8ab95ef3c6024fc5dc
Tx public key: cd0132bc2c8c13a6850a9fc1df23b231fd501d5007a92ebc575bc4909be50dda
Timestamp: 1762016472 Timestamp [UCT]: 2025-11-01 17:01:12 Age [y:d:h:m:s]: 00:007:10:51:55
Block: 1402775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5331 RingCT/type: yes/0
Extra: 01cd0132bc2c8c13a6850a9fc1df23b231fd501d5007a92ebc575bc4909be50dda02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1e8a2d3313d7c3ddddb65a4537e5855292db096adf5b58e5896f9e4b8fb13e 0.600000000000 1891094 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": 1402785, "vin": [ { "gen": { "height": 1402775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1e8a2d3313d7c3ddddb65a4537e5855292db096adf5b58e5896f9e4b8fb13e" } } ], "extra": [ 1, 205, 1, 50, 188, 44, 140, 19, 166, 133, 10, 159, 193, 223, 35, 178, 49, 253, 80, 29, 80, 7, 169, 46, 188, 87, 91, 196, 144, 155, 229, 13, 218, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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