Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9048e78187664f744e356266c7380982eba2ab6ae66f7e43b85b3a353bd4c713

Tx prefix hash: f624b5aa92cd638ed87d7da2829d21d9cf0ab2b68b35e2de5b0e6c7cc4fee322
Tx public key: 1f9ecc2430c584f52005f69ff4aebb28acebd9fcf4a8d537bc573ef06aa87bd6
Timestamp: 1703563973 Timestamp [UCT]: 2023-12-26 04:12:53 Age [y:d:h:m:s]: 01:097:02:38:09
Block: 921291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330518 RingCT/type: yes/0
Extra: 011f9ecc2430c584f52005f69ff4aebb28acebd9fcf4a8d537bc573ef06aa87bd602110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcdb6b1d10cbd7242b78162d94e492d0e54006c4a55e2827916b9ec4e8b55b72 0.600000000000 1378977 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": 921301, "vin": [ { "gen": { "height": 921291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcdb6b1d10cbd7242b78162d94e492d0e54006c4a55e2827916b9ec4e8b55b72" } } ], "extra": [ 1, 31, 158, 204, 36, 48, 197, 132, 245, 32, 5, 246, 159, 244, 174, 187, 40, 172, 235, 217, 252, 244, 168, 213, 55, 188, 87, 62, 240, 106, 168, 123, 214, 2, 17, 0, 0, 0, 7, 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