Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018c3fc222d9421f2b09f2ff19924455a0d83d3171c9ec31b1da7ff5ec42d9db

Tx prefix hash: 89e3bd6b8a3043ee03512db48052d0168c1ac67ec8b4f646e89ea5b390d014e6
Tx public key: 9251fb16620319b327ac4626d5cbd591b2bb3dc8541fa5f8d879cedf60b29c1a
Timestamp: 1694095544 Timestamp [UCT]: 2023-09-07 14:05:44 Age [y:d:h:m:s]: 01:264:08:06:00
Block: 842981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450066 RingCT/type: yes/0
Extra: 019251fb16620319b327ac4626d5cbd591b2bb3dc8541fa5f8d879cedf60b29c1a0211000000044b8f5122000000000000000000

1 output(s) for total of 0.988220994000 dcy

stealth address amount amount idx
00: 9619fb988c3321782a94c71fb67e314c7f10eb21fcdc556546ec6a99e640e759 0.988220994000 1296163 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": 842991, "vin": [ { "gen": { "height": 842981 } } ], "vout": [ { "amount": 988220994, "target": { "key": "9619fb988c3321782a94c71fb67e314c7f10eb21fcdc556546ec6a99e640e759" } } ], "extra": [ 1, 146, 81, 251, 22, 98, 3, 25, 179, 39, 172, 70, 38, 213, 203, 213, 145, 178, 187, 61, 200, 84, 31, 165, 248, 216, 121, 206, 223, 96, 178, 156, 26, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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