Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33b5d46ee5d03782dd8eeba666568a298635c131f936608bd6d69165356d25f0

Tx prefix hash: 7fd5a889dbdbdfbb745add52cff47b6ecb07eec4c39c3de66a411f9b7990f843
Tx public key: aef644ff65d7d6862af9703c2dc62cc096b6e5d63a5ed797d3fa4dc2e89d8fbd
Timestamp: 1708994747 Timestamp [UCT]: 2024-02-27 00:45:47 Age [y:d:h:m:s]: 01:102:11:36:20
Block: 966324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334304 RingCT/type: yes/0
Extra: 01aef644ff65d7d6862af9703c2dc62cc096b6e5d63a5ed797d3fa4dc2e89d8fbd02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3b048ae659c7a757f1d3dbce372f2fad56656953f683354083bddf82489d955 0.600000000000 1426081 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": 966334, "vin": [ { "gen": { "height": 966324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3b048ae659c7a757f1d3dbce372f2fad56656953f683354083bddf82489d955" } } ], "extra": [ 1, 174, 246, 68, 255, 101, 215, 214, 134, 42, 249, 112, 60, 45, 198, 44, 192, 150, 182, 229, 214, 58, 94, 215, 151, 211, 250, 77, 194, 232, 157, 143, 189, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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