Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f6c938eeaffffc68e300cd0a0dca4ff337216289c58bf17ad26a272e592f004

Tx prefix hash: bbfc3a2202e6a3234aef26a389dba7eaaacf940e2b9e7481591d60f303404f08
Tx public key: 8cc5f404d611b6d62e2682cb0411722cd01fecb86a8bea982cc3524cf7e11a21
Timestamp: 1744297619 Timestamp [UCT]: 2025-04-10 15:06:59 Age [y:d:h:m:s]: 00:052:12:03:04
Block: 1258494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37569 RingCT/type: yes/0
Extra: 018cc5f404d611b6d62e2682cb0411722cd01fecb86a8bea982cc3524cf7e11a210211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803c2d4ada78eaf1d8b2ea2109b544c7f24c89f49f5bcde0e4c5471b532617a8 0.600000000000 1745627 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": 1258504, "vin": [ { "gen": { "height": 1258494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803c2d4ada78eaf1d8b2ea2109b544c7f24c89f49f5bcde0e4c5471b532617a8" } } ], "extra": [ 1, 140, 197, 244, 4, 214, 17, 182, 214, 46, 38, 130, 203, 4, 17, 114, 44, 208, 31, 236, 184, 106, 139, 234, 152, 44, 195, 82, 76, 247, 225, 26, 33, 2, 17, 0, 0, 0, 2, 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