Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a11fd31ac3bbdb9584aebfcd8ce50f1d422d78a345ece05c0214225ed94d80a3

Tx prefix hash: 5416f53fe2a919c3d8f54e1f5c808f53868c8b9b1852b1bd22e217b785f2bbc5
Tx public key: 2ddc0258aaeec5165647e296e02b39f9f53ef2361ac0f328e6ffa0f6735f387b
Timestamp: 1709481162 Timestamp [UCT]: 2024-03-03 15:52:42 Age [y:d:h:m:s]: 01:057:04:16:39
Block: 970355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301885 RingCT/type: yes/0
Extra: 012ddc0258aaeec5165647e296e02b39f9f53ef2361ac0f328e6ffa0f6735f387b0211000000110011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e0505ce65a5bb2841c9b7e08c9b240b85e2f4e247a295ce46098905356de0f3 0.600000000000 1430208 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": 970365, "vin": [ { "gen": { "height": 970355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e0505ce65a5bb2841c9b7e08c9b240b85e2f4e247a295ce46098905356de0f3" } } ], "extra": [ 1, 45, 220, 2, 88, 170, 238, 197, 22, 86, 71, 226, 150, 224, 43, 57, 249, 245, 62, 242, 54, 26, 192, 243, 40, 230, 255, 160, 246, 115, 95, 56, 123, 2, 17, 0, 0, 0, 17, 0, 17, 5, 91, 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