Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 522cd3b1d593ec338c494a51724d32e51d3f7c9cdbd112f2fd4cc5f78bf59187

Tx prefix hash: 0950942d1a49f8438204d560c68efaead27e9cc8b28a2399ecc15c7d07f6faf0
Tx public key: 81de7a3f4221d82422dda0005b68db5d0c1b509cef3122e8a19f8f13a8d3a5da
Timestamp: 1722072094 Timestamp [UCT]: 2024-07-27 09:21:34 Age [y:d:h:m:s]: 00:248:21:56:33
Block: 1074731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177800 RingCT/type: yes/0
Extra: 0181de7a3f4221d82422dda0005b68db5d0c1b509cef3122e8a19f8f13a8d3a5da021100000017e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7de3727e7b4fa2604259a33d6383c27d04110468aae3fe2fb2b3dc780444f9 0.600000000000 1547248 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": 1074741, "vin": [ { "gen": { "height": 1074731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7de3727e7b4fa2604259a33d6383c27d04110468aae3fe2fb2b3dc780444f9" } } ], "extra": [ 1, 129, 222, 122, 63, 66, 33, 216, 36, 34, 221, 160, 0, 91, 104, 219, 93, 12, 27, 80, 156, 239, 49, 34, 232, 161, 159, 143, 19, 168, 211, 165, 218, 2, 17, 0, 0, 0, 23, 233, 20, 221, 21, 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