Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22649551adaf00c761e277c37f55de42abba8fad3057dcdf2071d08f42ab777

Tx prefix hash: b552a5465704cf45595c75dbc7c1324ca421e97d95086c5a33d8a5014d1bf2f5
Tx public key: f322823ec5f388b0d67b3997229d883f949e78f4a2e496473d8a3114903d27b3
Timestamp: 1682550664 Timestamp [UCT]: 2023-04-26 23:11:04 Age [y:d:h:m:s]: 01:357:18:48:52
Block: 747332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516974 RingCT/type: yes/0
Extra: 01f322823ec5f388b0d67b3997229d883f949e78f4a2e496473d8a3114903d27b30211000000027e406890000000000000000000

1 output(s) for total of 2.050118944000 dcy

stealth address amount amount idx
00: f4c54db6f8ac9b960c3d3cadcf26af9cfa4216f5d654b89c13e9e5a52580afe1 2.050118944000 1194989 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": 747342, "vin": [ { "gen": { "height": 747332 } } ], "vout": [ { "amount": 2050118944, "target": { "key": "f4c54db6f8ac9b960c3d3cadcf26af9cfa4216f5d654b89c13e9e5a52580afe1" } } ], "extra": [ 1, 243, 34, 130, 62, 197, 243, 136, 176, 214, 123, 57, 151, 34, 157, 136, 63, 148, 158, 120, 244, 162, 228, 150, 71, 61, 138, 49, 20, 144, 61, 39, 179, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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