Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f670d004b5add5c83d458f3637fa3d6e76cc42d5d048694ece0386f452a69e26

Tx prefix hash: 690b63f4ac017c76f42d0fdb774542dc4e529153c68a43a8a7983d4ab1ff29c5
Tx public key: c767a65f8fe34077f4334956df7d52b0962c0ab0e405876ea8afa572898c6620
Timestamp: 1705568513 Timestamp [UCT]: 2024-01-18 09:01:53 Age [y:d:h:m:s]: 01:291:06:12:07
Block: 937897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466969 RingCT/type: yes/0
Extra: 01c767a65f8fe34077f4334956df7d52b0962c0ab0e405876ea8afa572898c662002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7683d948a258035f945c05116bfba8760d6da7a3bb3e3d73012382b0e0ea42ff 0.600000000000 1395961 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": 937907, "vin": [ { "gen": { "height": 937897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7683d948a258035f945c05116bfba8760d6da7a3bb3e3d73012382b0e0ea42ff" } } ], "extra": [ 1, 199, 103, 166, 95, 143, 227, 64, 119, 244, 51, 73, 86, 223, 125, 82, 176, 150, 44, 10, 176, 228, 5, 135, 110, 168, 175, 165, 114, 137, 140, 102, 32, 2, 17, 0, 0, 0, 3, 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