Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4829e5231d1c60cd1c1cfe267cb469a13fec05a101eafa0a57d02207eca41f8

Tx prefix hash: 194e6931a4e571596272d4dd77545f77cc13fd3bac5a17f3e1f8413a77bd3e79
Tx public key: d4e5e89978f617d1f6a2506901395257103769adc812f400ab0dd7ac29bff61f
Timestamp: 1674702476 Timestamp [UCT]: 2023-01-26 03:07:56 Age [y:d:h:m:s]: 02:286:08:50:24
Block: 682890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724029 RingCT/type: yes/0
Extra: 01d4e5e89978f617d1f6a2506901395257103769adc812f400ab0dd7ac29bff61f0211000000045029cbac000000000000000000

1 output(s) for total of 3.351983616000 dcy

stealth address amount amount idx
00: 0ee7275910cc3ec5ae067f6f6304ae42ff04c61cb6d3065393dfb94e4f5c7e23 3.351983616000 1125031 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": 682900, "vin": [ { "gen": { "height": 682890 } } ], "vout": [ { "amount": 3351983616, "target": { "key": "0ee7275910cc3ec5ae067f6f6304ae42ff04c61cb6d3065393dfb94e4f5c7e23" } } ], "extra": [ 1, 212, 229, 232, 153, 120, 246, 23, 209, 246, 162, 80, 105, 1, 57, 82, 87, 16, 55, 105, 173, 200, 18, 244, 0, 171, 13, 215, 172, 41, 191, 246, 31, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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