Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3af8041f60fe325771e8aa99a562ec7a08c3d83701da259fd9792a316ba3134

Tx prefix hash: 5b697061c7cb0a61ba10b34b8f8574fcfaf6eb4757b0a1e902aa5d8043d71b34
Tx public key: 316a2730d62380bb49685ce8cfcfa5feac69f08be003a85eebea825e66a6eeae
Timestamp: 1702226163 Timestamp [UCT]: 2023-12-10 16:36:03 Age [y:d:h:m:s]: 01:333:09:28:43
Block: 910195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497141 RingCT/type: yes/0
Extra: 01316a2730d62380bb49685ce8cfcfa5feac69f08be003a85eebea825e66a6eeae021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b1b508369a0d7d4b5529d0d8454e1c8eeb828aa739ff70ba83569a238c98a50 0.600000000000 1367340 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": 910205, "vin": [ { "gen": { "height": 910195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b1b508369a0d7d4b5529d0d8454e1c8eeb828aa739ff70ba83569a238c98a50" } } ], "extra": [ 1, 49, 106, 39, 48, 214, 35, 128, 187, 73, 104, 92, 232, 207, 207, 165, 254, 172, 105, 240, 139, 224, 3, 168, 94, 235, 234, 130, 94, 102, 166, 238, 174, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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