Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987acc26fbf6168301c61c0ad77d8176382fa9ae424084d217a6832e05d66eb9

Tx prefix hash: 9585c2f4f7a466609f9e95b49ebc57ac4db9577a40e6db3d40473b76383d9919
Tx public key: a10f39276af1bc318281e2a0a0541e47e053f86b7d3756ae14d929f436bcb18d
Timestamp: 1742761147 Timestamp [UCT]: 2025-03-23 20:19:07 Age [y:d:h:m:s]: 00:237:03:04:22
Block: 1245781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167206 RingCT/type: yes/0
Extra: 01a10f39276af1bc318281e2a0a0541e47e053f86b7d3756ae14d929f436bcb18d021100000005c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5018fbaca2b1a5533b6f103e3301b98a56cf93335e0a3b49bb971547c487dff 0.600000000000 1732772 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": 1245791, "vin": [ { "gen": { "height": 1245781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5018fbaca2b1a5533b6f103e3301b98a56cf93335e0a3b49bb971547c487dff" } } ], "extra": [ 1, 161, 15, 57, 39, 106, 241, 188, 49, 130, 129, 226, 160, 160, 84, 30, 71, 224, 83, 248, 107, 125, 55, 86, 174, 20, 217, 41, 244, 54, 188, 177, 141, 2, 17, 0, 0, 0, 5, 198, 116, 9, 88, 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