Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e212f45c82623e6222ed9de5160de68184086c530635a62e2ffbce55435a6e8d

Tx prefix hash: 9f4de6ef21b0f7c8ba595d9d95acfb0cf9bff0e0f5ecca5421cda1dcc202c1ef
Tx public key: 8c548a35bd0478f27fe028294f6096807e4c7df20bdab6d922edff37799b03a3
Timestamp: 1718816867 Timestamp [UCT]: 2024-06-19 17:07:47 Age [y:d:h:m:s]: 00:187:09:06:59
Block: 1047744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134113 RingCT/type: yes/0
Extra: 018c548a35bd0478f27fe028294f6096807e4c7df20bdab6d922edff37799b03a30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69336a792774fc69d4d514ef2ebbaa54a23ec7eaf3011df90edc9ac2d35b2842 0.600000000000 1517647 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": 1047754, "vin": [ { "gen": { "height": 1047744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69336a792774fc69d4d514ef2ebbaa54a23ec7eaf3011df90edc9ac2d35b2842" } } ], "extra": [ 1, 140, 84, 138, 53, 189, 4, 120, 242, 127, 224, 40, 41, 79, 96, 150, 128, 126, 76, 125, 242, 11, 218, 182, 217, 34, 237, 255, 55, 121, 155, 3, 163, 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