Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebf68f55e1899b8548727737b80a77b7be50dc3a7aabc2ef0b9c79070d92d68f

Tx prefix hash: 41a0266a6368c7e262a41097d8b7b7ce8a73488402636f127ac0ceee48d63be3
Tx public key: 8c02b58314a6056cd0d650bc47380aa8edb542a4fc2d02992a8251ca960f4204
Timestamp: 1704333916 Timestamp [UCT]: 2024-01-04 02:05:16 Age [y:d:h:m:s]: 01:311:16:06:06
Block: 927685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481564 RingCT/type: yes/0
Extra: 018c02b58314a6056cd0d650bc47380aa8edb542a4fc2d02992a8251ca960f420402110000000ae08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c94b5a9c9f72944df7f4c36cf9927679364b5e583c2abba2ace98a4a94375b04 0.600000000000 1385521 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": 927695, "vin": [ { "gen": { "height": 927685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c94b5a9c9f72944df7f4c36cf9927679364b5e583c2abba2ace98a4a94375b04" } } ], "extra": [ 1, 140, 2, 181, 131, 20, 166, 5, 108, 208, 214, 80, 188, 71, 56, 10, 168, 237, 181, 66, 164, 252, 45, 2, 153, 42, 130, 81, 202, 150, 15, 66, 4, 2, 17, 0, 0, 0, 10, 224, 133, 50, 182, 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