Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095cb17014549240266c587d77915fadb7a534ee67dbe4042ba147056804f5f2

Tx prefix hash: 38f2fc7e910043f32fc354c95f8615570e4df3b57ff3f715693a11b89d3418f4
Tx public key: 10637584fd3e7fa7dcdf08b48e5ef10ebc36e1e5658c694c7246a071c0f7a30e
Timestamp: 1732281428 Timestamp [UCT]: 2024-11-22 13:17:08 Age [y:d:h:m:s]: 00:001:16:51:06
Block: 1159276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1215 RingCT/type: yes/0
Extra: 0110637584fd3e7fa7dcdf08b48e5ef10ebc36e1e5658c694c7246a071c0f7a30e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc66de6f6c752224144e7c1d8867d21eb29ba93f204feafbde3f5689535fff7 0.600000000000 1644909 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": 1159286, "vin": [ { "gen": { "height": 1159276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc66de6f6c752224144e7c1d8867d21eb29ba93f204feafbde3f5689535fff7" } } ], "extra": [ 1, 16, 99, 117, 132, 253, 62, 127, 167, 220, 223, 8, 180, 142, 94, 241, 14, 188, 54, 225, 229, 101, 140, 105, 76, 114, 70, 160, 113, 192, 247, 163, 14, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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