Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c49088806e343f3583dfe63f9e1d76db27c16d3812f5d4186205e8256773219

Tx prefix hash: f87ea43a8560f2812fd28a61718f24ecf660f0998eb852a5f4b580df10e8d4ed
Tx public key: 35a7f4375db9663fb36b6d6dd7200f7dc6a82676daa2a9274f2c8c463d835861
Timestamp: 1703229035 Timestamp [UCT]: 2023-12-22 07:10:35 Age [y:d:h:m:s]: 01:101:22:58:09
Block: 918515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333977 RingCT/type: yes/0
Extra: 0135a7f4375db9663fb36b6d6dd7200f7dc6a82676daa2a9274f2c8c463d83586102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 199151b78927191f3677f94ecdcf65c83f1e435f3580b252446d4f4682e1351b 0.600000000000 1376159 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": 918525, "vin": [ { "gen": { "height": 918515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "199151b78927191f3677f94ecdcf65c83f1e435f3580b252446d4f4682e1351b" } } ], "extra": [ 1, 53, 167, 244, 55, 93, 185, 102, 63, 179, 107, 109, 109, 215, 32, 15, 125, 198, 168, 38, 118, 218, 162, 169, 39, 79, 44, 140, 70, 61, 131, 88, 97, 2, 17, 0, 0, 0, 4, 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