Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d40eff9079bdc68d2e894f8bf59027072555d3c490aa0f0fdf6d19e65b13cc

Tx prefix hash: 83bb7877089a4e4639f602d3b5313ab6ce4de55bcfa06769b420b8839c6b5ca8
Tx public key: 39edf674d2178dd2e5f3d0dbd04e53add8ee089fbf81bf689cd13e89ee18715a
Timestamp: 1705167006 Timestamp [UCT]: 2024-01-13 17:30:06 Age [y:d:h:m:s]: 01:355:20:14:17
Block: 934567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513220 RingCT/type: yes/0
Extra: 0139edf674d2178dd2e5f3d0dbd04e53add8ee089fbf81bf689cd13e89ee18715a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 964f9e284d7823d852fd12b6fd3696c722ef714dbc04ec28588ac20d0b2b6b22 0.600000000000 1392581 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": 934577, "vin": [ { "gen": { "height": 934567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "964f9e284d7823d852fd12b6fd3696c722ef714dbc04ec28588ac20d0b2b6b22" } } ], "extra": [ 1, 57, 237, 246, 116, 210, 23, 141, 210, 229, 243, 208, 219, 208, 78, 83, 173, 216, 238, 8, 159, 191, 129, 191, 104, 156, 209, 62, 137, 238, 24, 113, 90, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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