Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320c529adf3011b2de2947ddbfd05febbc83a290ca3fab8461e91d00ab8cc2bf

Tx prefix hash: a04ca08b3d7eaec966984dc1c36f9756b358ae24f922cf7a9901e9d4201a4a5b
Tx public key: da3338683f905db710a2c5e6a3a2a101a84c42f37b69e87a8007d32619597763
Timestamp: 1715297577 Timestamp [UCT]: 2024-05-09 23:32:57 Age [y:d:h:m:s]: 01:007:03:05:53
Block: 1018569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266023 RingCT/type: yes/0
Extra: 01da3338683f905db710a2c5e6a3a2a101a84c42f37b69e87a8007d3261959776302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0919c096e6bfbc002a4e2b0481a97b2008c917d84207d83949bbf94735790f7a 0.600000000000 1482362 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": 1018579, "vin": [ { "gen": { "height": 1018569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0919c096e6bfbc002a4e2b0481a97b2008c917d84207d83949bbf94735790f7a" } } ], "extra": [ 1, 218, 51, 56, 104, 63, 144, 93, 183, 16, 162, 197, 230, 163, 162, 161, 1, 168, 76, 66, 243, 123, 105, 232, 122, 128, 7, 211, 38, 25, 89, 119, 99, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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