Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15262a24962fd6481f47e85b4e054cf7d3e72f180a985261f6fdb4f37ae336b

Tx prefix hash: 30ab154933e8e683f7bca1799651f24261d02970e0aa94e6be6fecabfcbd940a
Tx public key: 0d855a89bda792d2c464e87fcec343d268e4518612feee906d8b7fc2b5032843
Timestamp: 1696323363 Timestamp [UCT]: 2023-10-03 08:56:03 Age [y:d:h:m:s]: 01:224:00:50:31
Block: 861469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421193 RingCT/type: yes/0
Extra: 010d855a89bda792d2c464e87fcec343d268e4518612feee906d8b7fc2b50328430211000000014b8f5122000000000000000000

1 output(s) for total of 0.858214069000 dcy

stealth address amount amount idx
00: 1df505fd5d6b3cba0f1f6cda450ba0d4b8fa84ea143f927d8c5e2147939f8a85 0.858214069000 1315813 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": 861479, "vin": [ { "gen": { "height": 861469 } } ], "vout": [ { "amount": 858214069, "target": { "key": "1df505fd5d6b3cba0f1f6cda450ba0d4b8fa84ea143f927d8c5e2147939f8a85" } } ], "extra": [ 1, 13, 133, 90, 137, 189, 167, 146, 210, 196, 100, 232, 127, 206, 195, 67, 210, 104, 228, 81, 134, 18, 254, 238, 144, 109, 139, 127, 194, 181, 3, 40, 67, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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