Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87647dc3301227e511e0c8ffbe2bcc3fe7dec45a94b0227266dadb670177d0c7

Tx prefix hash: 8d1f123b84e286874ac96c2584495659896afc56e4e1da126e5d22d4ca650a1f
Tx public key: 1d1d99deb10f0238a3d96c28edbeedc1a7238e413f739d4e2e1dcaf8e1f098a6
Timestamp: 1708380677 Timestamp [UCT]: 2024-02-19 22:11:17 Age [y:d:h:m:s]: 01:058:00:02:56
Block: 961223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302473 RingCT/type: yes/0
Extra: 011d1d99deb10f0238a3d96c28edbeedc1a7238e413f739d4e2e1dcaf8e1f098a602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fc0573505795a228de6821ec65d4944164301b2e35aa65ed3364e7475a71105 0.600000000000 1420828 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": 961233, "vin": [ { "gen": { "height": 961223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fc0573505795a228de6821ec65d4944164301b2e35aa65ed3364e7475a71105" } } ], "extra": [ 1, 29, 29, 153, 222, 177, 15, 2, 56, 163, 217, 108, 40, 237, 190, 237, 193, 167, 35, 142, 65, 63, 115, 157, 78, 46, 29, 202, 248, 225, 240, 152, 166, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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