Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e405cfca9a795b93f6c1fbf6b7296ddc6be715c82fc20189ee5bce042e0fc4f1

Tx prefix hash: bf6cedf029dc994f265ef1f1f5e4e77d3f447720d1784cd153528b5cd67a8e7a
Tx public key: aaea3c8a87f3c93376a7128d1d9179705bc3efc97baebb44986d7b29d98c8bd2
Timestamp: 1733168460 Timestamp [UCT]: 2024-12-02 19:41:00 Age [y:d:h:m:s]: 00:111:15:16:28
Block: 1166632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79575 RingCT/type: yes/0
Extra: 01aaea3c8a87f3c93376a7128d1d9179705bc3efc97baebb44986d7b29d98c8bd20211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1f4ce1f8c4626cf529a7ce94c2af4e9d589acf4dc098581e16aabeadea0ac00 0.600000000000 1652321 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": 1166642, "vin": [ { "gen": { "height": 1166632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1f4ce1f8c4626cf529a7ce94c2af4e9d589acf4dc098581e16aabeadea0ac00" } } ], "extra": [ 1, 170, 234, 60, 138, 135, 243, 201, 51, 118, 167, 18, 141, 29, 145, 121, 112, 91, 195, 239, 201, 123, 174, 187, 68, 152, 109, 123, 41, 217, 140, 139, 210, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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