Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35804399a30e0d2eb16188e6af819d9b15e167f50984cd053b034b7684c6f539

Tx prefix hash: 6fd4bbe5ec8980ec61bb62394c077fa2592a48642f81da63687b19398cdd7b0d
Tx public key: f37afc6923fc8050bcf21760c6fa0bb95a7c9b6d78248aa4252dac8dc8aee2e8
Timestamp: 1720269241 Timestamp [UCT]: 2024-07-06 12:34:01 Age [y:d:h:m:s]: 00:284:00:45:30
Block: 1059785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202950 RingCT/type: yes/0
Extra: 01f37afc6923fc8050bcf21760c6fa0bb95a7c9b6d78248aa4252dac8dc8aee2e802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f38f907bf1be84f6a0f18295ed98a24be6cac2e9604ada0630988878d55aa41 0.600000000000 1530256 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": 1059795, "vin": [ { "gen": { "height": 1059785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f38f907bf1be84f6a0f18295ed98a24be6cac2e9604ada0630988878d55aa41" } } ], "extra": [ 1, 243, 122, 252, 105, 35, 252, 128, 80, 188, 242, 23, 96, 198, 250, 11, 185, 90, 124, 155, 109, 120, 36, 138, 164, 37, 45, 172, 141, 200, 174, 226, 232, 2, 17, 0, 0, 0, 1, 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