Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c4a24fa322c71f325cc6db7ea37c3dc620eaf9f4b0b25a1fcfa8bccab176489

Tx prefix hash: 6735f2dd4fb68223949412506cd8fd9d9f23ab6e6f3f1ee9cfcf53951657dd35
Tx public key: 558617c82b7181e423625edd38866da1f29bcf150f8e64d8dc4c06d59537bd52
Timestamp: 1720970835 Timestamp [UCT]: 2024-07-14 15:27:15 Age [y:d:h:m:s]: 00:266:15:21:31
Block: 1065610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190486 RingCT/type: yes/0
Extra: 01558617c82b7181e423625edd38866da1f29bcf150f8e64d8dc4c06d59537bd5202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 374716640ff39ea8e3ae83377dcbf7073e6e2d51764c509f16c6f78c41d97a9f 0.600000000000 1536159 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": 1065620, "vin": [ { "gen": { "height": 1065610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "374716640ff39ea8e3ae83377dcbf7073e6e2d51764c509f16c6f78c41d97a9f" } } ], "extra": [ 1, 85, 134, 23, 200, 43, 113, 129, 228, 35, 98, 94, 221, 56, 134, 109, 161, 242, 155, 207, 21, 15, 142, 100, 216, 220, 76, 6, 213, 149, 55, 189, 82, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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