Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67bcc797b0a9216632a62c2737d8aef991e16e21fc8bbaa78b1f1576ad8d579

Tx prefix hash: e4fcaf19fdac9a112d65c19d6f131b4d1c32b915ddece6079226f71d072ccb7c
Tx public key: 04a74aa1b19364a2f46f4f5adbe977963073356d2bb9fd18aaa2128148769f1a
Timestamp: 1723979512 Timestamp [UCT]: 2024-08-18 11:11:52 Age [y:d:h:m:s]: 00:229:13:05:01
Block: 1090550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163924 RingCT/type: yes/0
Extra: 0104a74aa1b19364a2f46f4f5adbe977963073356d2bb9fd18aaa2128148769f1a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f274bcff588efcb1a0970a3766daeee24faf2833a3968f0f9a7eb5ff33369b2 0.600000000000 1565173 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": 1090560, "vin": [ { "gen": { "height": 1090550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f274bcff588efcb1a0970a3766daeee24faf2833a3968f0f9a7eb5ff33369b2" } } ], "extra": [ 1, 4, 167, 74, 161, 177, 147, 100, 162, 244, 111, 79, 90, 219, 233, 119, 150, 48, 115, 53, 109, 43, 185, 253, 24, 170, 162, 18, 129, 72, 118, 159, 26, 2, 17, 0, 0, 0, 7, 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