Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12d99c9c593db19dea4ee748c077d44e76a866a96e8380b8df86f4801b78b0ce

Tx prefix hash: 460c088eca4f6dd5ee4c5a5462d46908e4eb28f072199c94cf3796f33cfe1af6
Tx public key: dec5c34e10a378e1fcf555d3264f20761cac41ee2d393c062db92ecba5caba3e
Timestamp: 1681350055 Timestamp [UCT]: 2023-04-13 01:40:55 Age [y:d:h:m:s]: 01:274:10:55:00
Block: 737361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457664 RingCT/type: yes/0
Extra: 01dec5c34e10a378e1fcf555d3264f20761cac41ee2d393c062db92ecba5caba3e0211000000015029cbac000000000000000000

1 output(s) for total of 2.212163058000 dcy

stealth address amount amount idx
00: d59d5c68343d20b26b9afd5ff171702d05108c9e8f0c7d4551caf66b8e376a50 2.212163058000 1183908 of 0

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": 737371, "vin": [ { "gen": { "height": 737361 } } ], "vout": [ { "amount": 2212163058, "target": { "key": "d59d5c68343d20b26b9afd5ff171702d05108c9e8f0c7d4551caf66b8e376a50" } } ], "extra": [ 1, 222, 197, 195, 78, 16, 163, 120, 225, 252, 245, 85, 211, 38, 79, 32, 118, 28, 172, 65, 238, 45, 57, 60, 6, 45, 185, 46, 203, 165, 202, 186, 62, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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