Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b820fe149b6c2de2262d74504d275bc7f3039ec523401a11b5de127a350389d4

Tx prefix hash: fdedc7cb065ba1d5f3a8bd6d1311e131be896b14776f22679abbeef422f771f4
Tx public key: b8e7b7cd39a80ee3aa1fabd63b0bb22b5c46757a67cefd4a879a6475d28600a6
Timestamp: 1715544706 Timestamp [UCT]: 2024-05-12 20:11:46 Age [y:d:h:m:s]: 00:332:15:45:05
Block: 1020646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237753 RingCT/type: yes/0
Extra: 01b8e7b7cd39a80ee3aa1fabd63b0bb22b5c46757a67cefd4a879a6475d28600a602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdeb3608adc2bd036849ff3f381ffd979d3baa9e30fda8b1ed765e503f87336c 0.600000000000 1484727 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": 1020656, "vin": [ { "gen": { "height": 1020646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdeb3608adc2bd036849ff3f381ffd979d3baa9e30fda8b1ed765e503f87336c" } } ], "extra": [ 1, 184, 231, 183, 205, 57, 168, 14, 227, 170, 31, 171, 214, 59, 11, 178, 43, 92, 70, 117, 122, 103, 206, 253, 74, 135, 154, 100, 117, 210, 134, 0, 166, 2, 17, 0, 0, 0, 6, 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