Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd8e4b18b7064945298a14d80ad808a045ed1b3c56104c04b0cac846b051ac21

Tx prefix hash: d72091070214f3a987f078ab39e9ed221b6d76bff4d032986722f23a402a9470
Tx public key: a3dce4209be10e8aa3a943af6d3f7f201ac054783bd680a1e8885b0b694347d9
Timestamp: 1727689990 Timestamp [UCT]: 2024-09-30 09:53:10 Age [y:d:h:m:s]: 01:062:00:13:42
Block: 1121313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302727 RingCT/type: yes/0
Extra: 01a3dce4209be10e8aa3a943af6d3f7f201ac054783bd680a1e8885b0b694347d902110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4df0defe4f62a868684df7270dee54cb8f59d8dd5bf6e492398609387da3cd9d 0.600000000000 1603540 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": 1121323, "vin": [ { "gen": { "height": 1121313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4df0defe4f62a868684df7270dee54cb8f59d8dd5bf6e492398609387da3cd9d" } } ], "extra": [ 1, 163, 220, 228, 32, 155, 225, 14, 138, 163, 169, 67, 175, 109, 63, 127, 32, 26, 192, 84, 120, 59, 214, 128, 161, 232, 136, 91, 11, 105, 67, 71, 217, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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