Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e4f09770dc2f0e604b2ce0285d63b3d0757d40f2543fa515a13fd3a264a60e

Tx prefix hash: 06ccd4de7286a9e3aee73d2924f9fcfeffcaff2ba60dfa376616b9b963a2826a
Tx public key: 4bfc42f843cf9e23cf2a7df827b5fe6b885b2ae8013ef8f42e817bbdaa9ad556
Timestamp: 1704286317 Timestamp [UCT]: 2024-01-03 12:51:57 Age [y:d:h:m:s]: 02:000:12:31:40
Block: 927279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520147 RingCT/type: yes/0
Extra: 014bfc42f843cf9e23cf2a7df827b5fe6b885b2ae8013ef8f42e817bbdaa9ad5560211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09839e1da9ca8c5eaa3832e797cba3b3be9d64ff0fb96f2345d2fcd4ff8d38a8 0.600000000000 1385111 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": 927289, "vin": [ { "gen": { "height": 927279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09839e1da9ca8c5eaa3832e797cba3b3be9d64ff0fb96f2345d2fcd4ff8d38a8" } } ], "extra": [ 1, 75, 252, 66, 248, 67, 207, 158, 35, 207, 42, 125, 248, 39, 181, 254, 107, 136, 91, 42, 232, 1, 62, 248, 244, 46, 129, 123, 189, 170, 154, 213, 86, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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