Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a7e3269e29031fd0bb96b70072736c7441be95fbc33c61c08dcf7cbe77c8e39

Tx prefix hash: c2ed79b13a1c0a59f38ff4d5c5b0358b0dc28c6756602943ac1412f41b5a911a
Tx public key: e0c62c25b736117550cfc5154a3a96654b03d635f84fa4849e6acfe40d6fce18
Timestamp: 1688055287 Timestamp [UCT]: 2023-06-29 16:14:47 Age [y:d:h:m:s]: 01:280:20:18:02
Block: 792998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461849 RingCT/type: yes/0
Extra: 01e0c62c25b736117550cfc5154a3a96654b03d635f84fa4849e6acfe40d6fce18021100000001272bcc39000000000000000000

1 output(s) for total of 1.447000153000 dcy

stealth address amount amount idx
00: a35c74e639e2fb8ee1d35909ed8fefa65e891829d231cd427ee4d8fde9d50cc9 1.447000153000 1243637 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": 793008, "vin": [ { "gen": { "height": 792998 } } ], "vout": [ { "amount": 1447000153, "target": { "key": "a35c74e639e2fb8ee1d35909ed8fefa65e891829d231cd427ee4d8fde9d50cc9" } } ], "extra": [ 1, 224, 198, 44, 37, 183, 54, 17, 117, 80, 207, 197, 21, 74, 58, 150, 101, 75, 3, 214, 53, 248, 79, 164, 132, 158, 106, 207, 228, 13, 111, 206, 24, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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