Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40a86f1652cd2fce985a741d49ae305f95ac66ac5e01435075648d67c2c2886

Tx prefix hash: 4372602a2a068a520ca2c0b8ae219eb6ea63d695c054d99f98b989dc6a6dd63c
Tx public key: ad10aceee4eeb45487448cebd291ad40308bcd34b5074f34d6e3ce65c50f3c62
Timestamp: 1632155299 Timestamp [UCT]: 2021-09-20 16:28:19 Age [y:d:h:m:s]: 04:045:22:38:30
Block: 337640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067222 RingCT/type: yes/0
Extra: 01ad10aceee4eeb45487448cebd291ad40308bcd34b5074f34d6e3ce65c50f3c620211000000353fc41461000000000000000000

1 output(s) for total of 46.693771591000 dcy

stealth address amount amount idx
00: deff1d534f9af8c19634f6922ed9b9300557b450bdf2ade12c8aa8c4c9a18fef 46.693771591000 695173 of 0

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": 337650, "vin": [ { "gen": { "height": 337640 } } ], "vout": [ { "amount": 46693771591, "target": { "key": "deff1d534f9af8c19634f6922ed9b9300557b450bdf2ade12c8aa8c4c9a18fef" } } ], "extra": [ 1, 173, 16, 172, 238, 228, 238, 180, 84, 135, 68, 140, 235, 210, 145, 173, 64, 48, 139, 205, 52, 181, 7, 79, 52, 214, 227, 206, 101, 197, 15, 60, 98, 2, 17, 0, 0, 0, 53, 63, 196, 20, 97, 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