Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3609df5fcac2b0c1f2af5f5ffc904b4a876d7b480d65d7e26eabbd7cca06e784

Tx prefix hash: 1342579ab0bf828a62ef30163e5671be446a867722f129937e16e0d07483f885
Tx public key: eb313fdc8d84a64058f5691d07ac4a7ece879d650178e5093fd8d531d6a21a2f
Timestamp: 1711220964 Timestamp [UCT]: 2024-03-23 19:09:24 Age [y:d:h:m:s]: 00:292:23:10:20
Block: 984793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209690 RingCT/type: yes/0
Extra: 01eb313fdc8d84a64058f5691d07ac4a7ece879d650178e5093fd8d531d6a21a2f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ddd3ba5a51487a7df9446306fef8a5d032a92ddb923697ebc8bbdb7d516e9c9 0.600000000000 1444966 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": 984803, "vin": [ { "gen": { "height": 984793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ddd3ba5a51487a7df9446306fef8a5d032a92ddb923697ebc8bbdb7d516e9c9" } } ], "extra": [ 1, 235, 49, 63, 220, 141, 132, 166, 64, 88, 245, 105, 29, 7, 172, 74, 126, 206, 135, 157, 101, 1, 120, 229, 9, 63, 216, 213, 49, 214, 162, 26, 47, 2, 17, 0, 0, 0, 4, 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