Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649a6ba9775cfde9a3d4f27444d7164af5e6b5e652fe8612fdc909bf5b28db28

Tx prefix hash: 4be005e42b0b91ef01c7f6adfab72d54d0ded5c78b4f50c8425c0fdda4d4fc2e
Tx public key: f1777443de59ea6b07aec6c34c8d75092c3e33c5d5f372f1624d038d40cc3974
Timestamp: 1693152483 Timestamp [UCT]: 2023-08-27 16:08:03 Age [y:d:h:m:s]: 02:132:08:04:08
Block: 835145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614395 RingCT/type: yes/0
Extra: 01f1777443de59ea6b07aec6c34c8d75092c3e33c5d5f372f1624d038d40cc397402110000000275e3f0e9000000000000000000

1 output(s) for total of 1.049102708000 dcy

stealth address amount amount idx
00: dfad6d069acae91041ada98f40271b082aa1735ad83ee9360e3edce1c7d458e6 1.049102708000 1287685 of 0

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": 835155, "vin": [ { "gen": { "height": 835145 } } ], "vout": [ { "amount": 1049102708, "target": { "key": "dfad6d069acae91041ada98f40271b082aa1735ad83ee9360e3edce1c7d458e6" } } ], "extra": [ 1, 241, 119, 116, 67, 222, 89, 234, 107, 7, 174, 198, 195, 76, 141, 117, 9, 44, 62, 51, 197, 213, 243, 114, 241, 98, 77, 3, 141, 64, 204, 57, 116, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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