Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7877593df40623b85598a4d851efefbd198f84d60cd228e9d7698e17f8a85992

Tx prefix hash: 331ce51dac403e5ef2d89abf2393328f4d1d69af1e355151a969cc93d9a6cf7a
Tx public key: 7e0b881000d6c7a11874e8632ea5de65de3bf047209aa10bff469cf32c7e40c0
Timestamp: 1723155864 Timestamp [UCT]: 2024-08-08 22:24:24 Age [y:d:h:m:s]: 00:295:19:13:14
Block: 1083714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211346 RingCT/type: yes/0
Extra: 017e0b881000d6c7a11874e8632ea5de65de3bf047209aa10bff469cf32c7e40c0021100000005e914dd15000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 0ac250589777ad08ee41f5acf210c0152665c6fb3529eefc958d85f7d09a6e3a 0.615600000000 1557733 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": 1083724, "vin": [ { "gen": { "height": 1083714 } } ], "vout": [ { "amount": 615600000, "target": { "key": "0ac250589777ad08ee41f5acf210c0152665c6fb3529eefc958d85f7d09a6e3a" } } ], "extra": [ 1, 126, 11, 136, 16, 0, 214, 199, 161, 24, 116, 232, 99, 46, 165, 222, 101, 222, 59, 240, 71, 32, 154, 161, 11, 255, 70, 156, 243, 44, 126, 64, 192, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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