Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27a01882c9a0610c00a44d8f18be5294c370edb80c8a3a7c81b8afc9dee2a0c5

Tx prefix hash: 905a9fc1440facced94af5b40c23da32d384f8ecd9e701f533919ceb1f06272b
Tx public key: e6501954f315968df8763e5a9c4654d37fc5bbd15a73c7501aa8da52c07b2720
Timestamp: 1704463900 Timestamp [UCT]: 2024-01-05 14:11:40 Age [y:d:h:m:s]: 01:052:10:10:24
Block: 928738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298550 RingCT/type: yes/0
Extra: 01e6501954f315968df8763e5a9c4654d37fc5bbd15a73c7501aa8da52c07b272002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ae78435db49b5ae7150a42db0c0d886c87a68846b148bc7c3238b9e783fa4a 0.600000000000 1386598 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": 928748, "vin": [ { "gen": { "height": 928738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ae78435db49b5ae7150a42db0c0d886c87a68846b148bc7c3238b9e783fa4a" } } ], "extra": [ 1, 230, 80, 25, 84, 243, 21, 150, 141, 248, 118, 62, 90, 156, 70, 84, 211, 127, 197, 187, 209, 90, 115, 199, 80, 26, 168, 218, 82, 192, 123, 39, 32, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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