Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4fad46dd3abc52f0cdf6c05cbdf5543e27a9f97ae40d0d99b13bceeba77c32

Tx prefix hash: 60929162729bee3ccbfc792eac35200b325d09a84f51a6da470dded7409a7b5c
Tx public key: 3f9bf0eb7f0f1c4753b6afe5e2b0c283f824f20d16f7229154d33ec4aee56d6d
Timestamp: 1714491531 Timestamp [UCT]: 2024-04-30 15:38:51 Age [y:d:h:m:s]: 01:191:10:40:50
Block: 1011887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395458 RingCT/type: yes/0
Extra: 013f9bf0eb7f0f1c4753b6afe5e2b0c283f824f20d16f7229154d33ec4aee56d6d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14663d9db6a21d331581b92026439d80d58a06f9f66790f75f337a41e687b325 0.600000000000 1474241 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": 1011897, "vin": [ { "gen": { "height": 1011887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14663d9db6a21d331581b92026439d80d58a06f9f66790f75f337a41e687b325" } } ], "extra": [ 1, 63, 155, 240, 235, 127, 15, 28, 71, 83, 182, 175, 229, 226, 176, 194, 131, 248, 36, 242, 13, 22, 247, 34, 145, 84, 211, 62, 196, 174, 229, 109, 109, 2, 17, 0, 0, 0, 2, 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