Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb10f306cd54a21b36fce1b94b89b9bf95d275537423d03c514e6172fabc469c

Tx prefix hash: 88b30f02e33e4f27315ac4adc19159d139eb3c722db8647d96f82e0ea207475f
Tx public key: de153a6bc5b4e0da53b8d48c6151ed88e520c54a4ba299d269760f933f8cfbe2
Timestamp: 1732838893 Timestamp [UCT]: 2024-11-29 00:08:13 Age [y:d:h:m:s]: 00:132:14:50:26
Block: 1163897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94594 RingCT/type: yes/0
Extra: 01de153a6bc5b4e0da53b8d48c6151ed88e520c54a4ba299d269760f933f8cfbe20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61e8165e09e341a25fe4a77647fd9caa4410ae684924f12535eaedfff6df7ad4 0.600000000000 1649566 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": 1163907, "vin": [ { "gen": { "height": 1163897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61e8165e09e341a25fe4a77647fd9caa4410ae684924f12535eaedfff6df7ad4" } } ], "extra": [ 1, 222, 21, 58, 107, 197, 180, 224, 218, 83, 184, 212, 140, 97, 81, 237, 136, 229, 32, 197, 74, 75, 162, 153, 210, 105, 118, 15, 147, 63, 140, 251, 226, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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