Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8030e30608c248f7daaf95e16191fe0e1109c0d6afc7e00fb4d7fb0b21068c8

Tx prefix hash: 14494062f70878bdd2c2e480650661a779ef1e0eb44317b5e9a6a5afb61ead1c
Tx public key: 6f69ac533f1711ed3e4b01ddb61034dc1eaebc5b8d3f2e167eea2bc7d1456ec1
Timestamp: 1709195684 Timestamp [UCT]: 2024-02-29 08:34:44 Age [y:d:h:m:s]: 00:245:08:58:57
Block: 967993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175669 RingCT/type: yes/0
Extra: 016f69ac533f1711ed3e4b01ddb61034dc1eaebc5b8d3f2e167eea2bc7d1456ec10211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efdccd7855db7e4b4a38b5366c1f2b07d38a51d83990c52a26d90b92e9326fe7 0.600000000000 1427788 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": 968003, "vin": [ { "gen": { "height": 967993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efdccd7855db7e4b4a38b5366c1f2b07d38a51d83990c52a26d90b92e9326fe7" } } ], "extra": [ 1, 111, 105, 172, 83, 63, 23, 17, 237, 62, 75, 1, 221, 182, 16, 52, 220, 30, 174, 188, 91, 141, 63, 46, 22, 126, 234, 43, 199, 209, 69, 110, 193, 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