Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b18d558477d291d0124c00965a6209cd4d1273abad991c71b79bcbaa9939928b

Tx prefix hash: bf477123e58010782b5607bf40de9c7b08fed50629119e0f4e2b54d32a47c474
Tx public key: 59cb43c0e6a447f81102d49cf9f1be45c8f4cd9a855d0c4cc87e4128434563a0
Timestamp: 1705309321 Timestamp [UCT]: 2024-01-15 09:02:01 Age [y:d:h:m:s]: 01:159:11:10:03
Block: 935746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374903 RingCT/type: yes/0
Extra: 0159cb43c0e6a447f81102d49cf9f1be45c8f4cd9a855d0c4cc87e4128434563a00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a424f30c0d2b67af0871d1595278f23e3a8b3661a6b91ef004c7bfa2687aae07 0.600000000000 1393762 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": 935756, "vin": [ { "gen": { "height": 935746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a424f30c0d2b67af0871d1595278f23e3a8b3661a6b91ef004c7bfa2687aae07" } } ], "extra": [ 1, 89, 203, 67, 192, 230, 164, 71, 248, 17, 2, 212, 156, 249, 241, 190, 69, 200, 244, 205, 154, 133, 93, 12, 76, 200, 126, 65, 40, 67, 69, 99, 160, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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