Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b0c3ba705d39f37e755ddea3eff42189ff6bd330c0d2932f2744296c75e6db

Tx prefix hash: d4dc231260b1ebc8d43111d0779e3283f7b6867e3ebf0ade0f4c0a77e63850a6
Tx public key: bd335af6c755a980a0388ad48015f442e4e9e08f97d132be8c254bd2a2dc8b93
Timestamp: 1618817009 Timestamp [UCT]: 2021-04-19 07:23:29 Age [y:d:h:m:s]: 04:200:07:29:58
Block: 243100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161755 RingCT/type: yes/0
Extra: 01bd335af6c755a980a0388ad48015f442e4e9e08f97d132be8c254bd2a2dc8b930211000000607071732b000000000000000000

1 output(s) for total of 96.052649316000 dcy

stealth address amount amount idx
00: 91557f0b69606204ee7ded43a318cbf9a9b66f64126a79db3f749142126142f0 96.052649316000 507212 of 0

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": 243110, "vin": [ { "gen": { "height": 243100 } } ], "vout": [ { "amount": 96052649316, "target": { "key": "91557f0b69606204ee7ded43a318cbf9a9b66f64126a79db3f749142126142f0" } } ], "extra": [ 1, 189, 51, 90, 246, 199, 85, 169, 128, 160, 56, 138, 212, 128, 21, 244, 66, 228, 233, 224, 143, 151, 209, 50, 190, 140, 37, 75, 210, 162, 220, 139, 147, 2, 17, 0, 0, 0, 96, 112, 113, 115, 43, 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