Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 817670bf9ab01a09144a70edf4155e7384c390726bda3917af2193e054f74882

Tx prefix hash: fd1ee6ec5e3f6742be9c6753f7832fe7049609c7ccf96870be0cf8b232edf52a
Tx public key: 74a0094fc7c72497f9cf88d5a3f236f1f1f1679c33197ba56f71e7c6f0109873
Timestamp: 1721262224 Timestamp [UCT]: 2024-07-18 00:23:44 Age [y:d:h:m:s]: 00:178:03:55:51
Block: 1068034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127459 RingCT/type: yes/0
Extra: 0174a0094fc7c72497f9cf88d5a3f236f1f1f1679c33197ba56f71e7c6f010987302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6f25d1ef3dee15cb640ff679ff2f6e0293b412616e136928d741ac2e2ffb15 0.600000000000 1539019 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": 1068044, "vin": [ { "gen": { "height": 1068034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6f25d1ef3dee15cb640ff679ff2f6e0293b412616e136928d741ac2e2ffb15" } } ], "extra": [ 1, 116, 160, 9, 79, 199, 199, 36, 151, 249, 207, 136, 213, 163, 242, 54, 241, 241, 241, 103, 156, 51, 25, 123, 165, 111, 113, 231, 198, 240, 16, 152, 115, 2, 17, 0, 0, 0, 4, 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