Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f78cea5e015ea628949f1460b658b5dbd47d56372c34232b6f83ac54367466

Tx prefix hash: 9742aa806e8ac62c8f90e85f5e626ccb802ae69a2ee87e8e93708ab52fbe2d25
Tx public key: d9fdef3d10d6b6ad4df4c4017a939c274898277a897eace9251eb0b51f1b1e04
Timestamp: 1741666553 Timestamp [UCT]: 2025-03-11 04:15:53 Age [y:d:h:m:s]: 00:255:13:02:54
Block: 1236724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180366 RingCT/type: yes/0
Extra: 01d9fdef3d10d6b6ad4df4c4017a939c274898277a897eace9251eb0b51f1b1e04021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b146fc8d8d407e0f807bc116d324ae28d911b7a8c2da46f14e11ca0f3cda15 0.600000000000 1723675 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": 1236734, "vin": [ { "gen": { "height": 1236724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b146fc8d8d407e0f807bc116d324ae28d911b7a8c2da46f14e11ca0f3cda15" } } ], "extra": [ 1, 217, 253, 239, 61, 16, 214, 182, 173, 77, 244, 196, 1, 122, 147, 156, 39, 72, 152, 39, 122, 137, 126, 172, 233, 37, 30, 176, 181, 31, 27, 30, 4, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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